Task template update based on task usage pattern

ABSTRACT

The usefulness of task templates can be maintained in a number of ways. Task templates can be updated on a client server from a remote task update server by initiating communication with the remote task update server, selecting a task template from a list of available task templates presented by the remote task update server, and downloading the selected task template to the client server in a format defined by a schema. Task templates can be updated on a client server by receiving a request from the client server, presenting a task template based on the request, receiving a selection of the task template, and transmitting the task template to the client server in a format defined by a schema. Task templates can also be managed by downloading task templates, assigning group names, and storing the downloaded task templates in a database.

BACKGROUND

Despite advances in technology, managing servers can be difficult. For example, a software manufacturer can sell a software package allowing a user of the software package to perform various functions for managing applications. The user of the software package can use the functions provided with the software package. However, the user may not know how to combine the functions to solve problems with the servers. Due to the vast number of options available, the user may ignore functionality or not even be aware that it exists.

Therefore, there exists ample room for improvement in technologies related to managing servers.

SUMMARY

A variety of technologies related to maintaining the usefulness of task templates can be applied. Such technologies can be used for updating task templates on a client server from a remote task update server (e.g., where the task templates are used to accomplish tasks for managing applications of a multi-server system). For example, a communication can be initiated with a remote task update server, and based on a list of available task templates, a selection of one or more task templates can be made. The selected task templates can be downloaded to the client server (e.g., in a format defined by a schema, such as XML or XrML). The list of available task templates can be recommended based on, for example, a profile or a pattern of usage. Updating task templates can be initiated via a task update tool.

Such technologies can be used to update task templates on a client server. For example, an update request can be received from a client server (e.g., by a remote task update server). Based on the request, one or more task templates can be presented (e.g., recommended based on a profile received with the update request). A selection can be received from the one or more presented task templates. The selected task templates can be downloaded to the client server (e.g., in a format defined by a schema). For example, the task templates can be downloaded to the client server automatically, or on a user-defined or automatically-defined schedule.

Such technologies can also be used to manage task templates. For example a task template can be downloaded (e.g., in a format defined by a schema) from a remote task update server. A group name can be assigned to the downloaded task template (e.g., by recording the group name in the task template schema). The downloaded task template can be stored in a database (e.g., in the format defined by the schema).

The foregoing and other objects, features, and advantages of the invention will become more apparent from the following detailed description, which proceeds with reference to the accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing an exemplary system for updating task templates.

FIG. 2 is a diagram showing an exemplary system for using tasks.

FIG. 3 is a flowchart showing an exemplary method for updating a task template.

FIG. 4 is a diagram showing an exemplary system for remote task template updating.

FIG. 5 is a diagram showing an exemplary user interface depicting a task profile tool.

FIG. 6 is a flowchart showing an exemplary method for recommending task templates using a profile.

FIG. 7 is a diagram showing an exemplary update tasks user interface.

FIG. 8 is a flowchart showing an exemplary method for updating task templates using a task update tool.

FIG. 9 is a diagram showing an exemplary user interface depicting an update tasks tool.

FIG. 10 is a diagram showing an exemplary task template schema.

FIG. 11 is a flowchart showing an exemplary method for updating task templates on a client server.

FIG. 12 is a flowchart showing an exemplary method for recommending task templates based on a pattern of usage.

FIG. 13 is a flowchart showing an exemplary method for storing task templates.

FIG. 14 is a diagram showing an exemplary user interface depicting display of task templates.

FIG. 15 is a flowchart showing an exemplary method for completing a task.

FIG. 16 is a diagram showing an exemplary multi-server system for performing tasks.

FIG. 17 is a block diagram illustrating an example of a computing environment that can be used to implement any of the technologies described herein.

FIG. 18 is block diagram illustrating an example of a computer system that can be used to implement any of the technologies described herein.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS EXAMPLE 1 Exemplary Task

In any of the examples herein, a task can represent work that is performed on a computer network (e.g., a multi-server computer environment of a business or organization). For example, a task can represent the retrieval of information that is displayed to a user of the network (e.g., for troubleshooting purposes). A task can also represent making a change to the network (e.g., changing settings in an application). A task can be performed, for example, by using a task template. For display purposes, a user interface element (e.g., a button, link) can be displayed for initiating a task.

Selecting (e.g., invoking) a task can result in displaying a user interface for accomplishing (e.g., completing) the task. For example, selecting a task (e.g., by selecting a user interface element associated with the task) can result in displaying a custom user interface that allows a user to make changes to a number of applications and computer servers on a network. For example, selecting a “manage licenses” task (e.g., selecting a button or link associated with the text “manage licenses”) can result in display of a custom user interface that allows a user of a network to manage licenses for users and devices across multiple servers and services. Selecting a task can also result in display of a user interface that is part of an application on a network (e.g., a user interface that is already native to an application). For example, selecting a “change password” task for a selected user can result in display of a “change password” user interface from a user management application.

Selecting a task can result in display of various types of user interfaces. For example, a wizard user interface can be displayed (e.g., where the user is directed through a series of step). A dialog can be displayed (e.g., the user can be asked to confirm the deletion of a user account). A view can also be displayed (e.g., a page allowing the user to configure various settings, such as web site settings).

EXAMPLE 2 Exemplary Task Template

In any of the examples herein, a task template can be used to accomplish (e.g., complete) a task. For example, a task template can be used to direct a user to a user interface for accomplishing a task. For example, a task template can comprise a location variable. The location variable can contain a location. The location can represent (e.g., be an address of) a user interface (e.g., a wizard, dialog, or view). For example, the location can represent a user interface by way of an API of an application. A task template can be in the format of a schema (e.g., an XML or XrML schema).

A task template can also be stored in a variety of ways and in a variety of locations. For example, task templates can be stored as data values in a tasks database (e.g., on a computer server). Task templates can also be stored as schemas (e.g., in a database, file, data store, or in another data storage location), such as an XML schema.

A task template can be updated. For example, a new task template can be downloaded to allow a user to accomplish the new task associated with the new task template. A task template can be downloaded in order to replace an existing task template (e.g., to provide updated functionality or to support a change to an application identified by a location variable of the task template). A task template can also be deleted or removed (e.g., from a tasks database on a computer server).

A task template can be used when a task is selected (e.g., invoked). For example, a task to add a new user to a network can be selected. In response, a location variable from a task template related to the task can be used to display a user interface identified by the location variable.

Selecting (e.g., invoking) or displaying a task template can comprise selecting or displaying an instance of the task template (e.g., displaying a user interface for accomplishing a task). An instance of a task template can be a specific occurrence of the task template. For example, a first instance of a task template can be displayed when a task template is selected (e.g., from a context-free task), and based on a location variable from the task template, a user interface of an application is displayed. A second instance of the same task template can also be displayed when the task template is selected (e.g., from a contextual task). In this way, multiple instances of the same task template can be selected and displayed.

The same task can be selected multiple times and multiple instances of the same task template displayed (e.g., at different times or at the same time). For example, an add user task can be selected multiple times and multiple instances of an add user task template can be displayed (e.g., multiple windows in a user interface, each window comprising fields for adding a user, such as: user name, real name, and password).

Or, different tasks can be selected and multiple instances of the same task template displayed. For example, an edit user task for a specific user can be selected and an instance of an edit user template can be displayed (e.g., filled in with the specific user's information). An edit user task for a different specific user can also be selected and an instance of the same edit user template can be displayed (e.g., filled in with the different specific user's information).

EXAMPLE 3 Exemplary Updating Task Templates

In any of the examples herein, a task can be kept up to date by updating task templates used to accomplish the task. For example, a customer (e.g., an individual, business, or organization) can purchase computer hardware and software (e.g., to be used in operating a business). The software can comprise a management application for managing (e.g., via tasks which are accomplished by task templates) a collection of applications across a number of computer servers (e.g., a number of computer servers comprising a multi-server system). The management application can be sold with a set of pre-installed task templates (e.g., by the software manufacturer) for accomplishing tasks. However, the pre-installed task templates may soon become out of date (e.g., as applications are updated with new features and functionality or as new applications are installed). In addition, the specific pre-installed task templates may not be useful to some customers. Therefore, updating task templates is an important aspect to maintaining their usefulness.

Task templates can be updated for a variety of reasons. An application can change (e.g., new features added), and in order for an existing task template to operate correctly with the new application (e.g., to display the correct user interface of the application), it can need to be updated. New task templates can be created to address the needs (e.g., workflow requirements) of specific customers (or specific types, groups, or categories of customers). For example, a new task template can be created for customers that operate high employee turnover businesses (e.g., hotel operations). Task templates can also be updated for many other reasons (e.g., task templates can be updated with a better recommended way to complete the task).

Updated task templates can be created and provided by a software manufacturer. For example, a software manufacturer that develops and sells a suite of server applications (including a management application that uses task templates to manage the server applications) can provide updated task templates to maintain the usefulness of the suite of server applications over its lifetime (e.g., 3-5 years). The software manufacturer can have employees dedicated to keeping task templates up to date (e.g., due to software changes) and developing new task templates.

Task templates can be updated by providing a list of recommended task templates (e.g., recommended based on various attributes of a customer, such as the types of tasks the customer performs). Task templates can also be updated by providing a list of optional task templates (e.g., task templates that are not specifically recommended by a task update server, but nevertheless may be of interest to a customer).

A customer can update task templates in a variety of ways. For example, a customer can connect to a remote task update server and download updated task templates. A customer can obtain updated task templates on removable storage media (e.g., a CD or DVD). A customer can also obtain updated task templates in other ways (e.g., via email).

EXAMPLE 4 Exemplary Patterns of Task Usage

In any of the examples herein, patterns of task usage can be identified. Patterns of task usage can be identified by tracking the task templates that are used by a user (or a group of users) of a computer server (e.g., using a management application on the computer server to manage various applications). Patterns of task usage can also be tracked based on the frequency of usage.

Patterns of task usage can be stored on a computer server (e.g., the computer server on which the task templates were invoked). Patterns of task usage can also be transmitted to a remote server (e.g., to a remote task update server of a software manufacturer).

Patterns of task usage can be analyzed (e.g., to identify trends of task usage or to recommend task template updates). For example, if a specific user (e.g., an IT administrator) frequently uses task templates to add, edit, or delete user accounts, the pattern of task usage can be analyzed to determine that the specific user often deals with user account management requests. Based on this pattern, the user can receive task template recommendations. For example, the user can receive a recommendation to download an updated task template for simplifying user account management (e.g., for more efficiently working with groups of accounts).

Profiles can be created based on patterns of task usage. For example, if a user frequently uses task templates to add, edit, or delete user accounts, a profile associated with the user can indicate high user turnover. The profile can then be used, for example, to recommend task template updates.

EXAMPLE 5 Exemplary Profile

In any of the examples herein, a profile can be created and used to recommend task template updates. A profile can be created based upon a pattern of task usage. For example, if a user frequently uses task templates to add, edit, or delete user accounts, a profile can be created and associated with the user (or an existing profile associated with the user can be updated) indicating that the user is involved with a high user turnover business. The profile can then be used, for example, to recommend task template updates. For example, other task templates associated with user management in a high turnover business can be recommended.

A profile can also be created by a software manufacturer. For example, a software manufacturer can create a “high turnover” profile or a “mobile users” profile. Task templates or groups of task templates can be associated with a profile. For example, a software manufacturer can associate task templates for managing user accounts with a “high turnover” profile.

A profile based upon a pattern of task usage can be created locally or remotely. For example, a management application of a multi-server system of a business can locally create and store profiles based on task template usage. In addition, patterns of task usage can be transmitted to a remote location. For example, patterns of task usage can be transmitted to a remote task update server (e.g., operated by a software manufacturer). The remote task update server can analyze the patterns of task usage and, based on the analysis, create a profile (or use an existing profile that matches the pattern) and recommend task template updates to a customer of the software manufacturer (e.g., a customer using software developed by the software manufacturer to operate a multi-server system). A profile can be created locally and then transmitted to a remote task update server.

A profile can also be created or assigned in other ways. For example, a profile can be created or assigned based upon information provided by a user (e.g., characteristics of a user's business, various categories or groups of task templates the user is interested in, or other information about the types of tasks performed by the user). This type of profile can be defined by the user's manual selection of preferences. For example, the user can select a business category (e.g., hotel, restaurant, medical, financial, retail). A user can select characteristics of the user's business (e.g., high employee turnover, branch offices). A user can select a category or group of task templates that the user is interested in (e.g., user management, network administration). A user can also select a pre-created profile (e.g., a profile created by a software manufacturer) that matches the type of activities the user expects to perform (e.g., high turnover, mobile users).

A profile can be used to recommend task template updates. For example, if a profile indicates a high turnover business (e.g., a “high turnover” profile), then task template updates related to user management can be recommended (e.g., task templates that a software manufacturer has associated with a “high turnover” profile). If a profile indicates mobile users, then task template updates related to maintaining mobile computer patch updates can be recommended.

One or more profiles can be associated with a user or customer (e.g., individual user, business, organization).

EXAMPLE 6 Exemplary Groups of Task Templates

In any of the examples herein, task templates can be organized into groups. A group can be identified by a group name, such as: “user management” or “network administration.” A task template can be assigned to (e.g., associated with) a group by, for example, recording a group name in a group name field of the task template (where the task template is defined by a schema comprising the group name field). For example, one or more task templates associated with managing user accounts can be grouped into a user management group. Groups can be associated with profiles. For example, a “user management” group of task templates can be associated with a “high turnover” profile.

Groups of Task Templates can be updated. For example, a user can select and download a group of task templates by making a single selection of the group, without having to select multiple individual task templates.

EXAMPLE 7 Exemplary Discovery of Task Templates

In any of the examples herein, task templates can be discovered (i.e., a customer can learn that updated task templates are available). Task templates can be discovered in a variety of ways. Task templates can be discovered based on a recommendation of task templates. For example, a recommendation can be based on a pattern of task usage. A recommendation can also be based on a profile. In this way, automated recommendations of task template updates can be made. For example, a remote task update server can automatically make recommendations of task template updates based on a profile of a user connected to (e.g., communicating with) the remote task update server. The user can be informed of these recommendations through a notification mechanism, such as email or through the management server user interface.

Task templates can be discovered based on a subscription. A subscription can comprise a subscription parameter that indicates a frequency at which to check for task template updates (e.g., with a remote task update server) as well as the preferred content of the subscription. For example, a subscription associated with a user, computer, or application can automatically check (e.g., without any involvement by a user) for task template updates on a periodic schedule (e.g., weekly or monthly). If task template updates are available (e.g., recommended task template updates based on a profile), then the updates can be automatically downloaded and stored. Or, if task template updates are available, a user can be prompted to download the updates as part of an automated process. In determining whether updates (recommended or optional) are available, a profile can be checked. For example, a management application can be associated with a subscription that checks weekly for task template updates. Recommended task template updates based on a profile associated with the management application can then be presented (e.g., and automatically downloaded or downloaded after confirmation).

Task templates can be discovered using a task update tool (e.g., a wizard). For example, a user can use a task update tool (e.g., a computer application providing a user interface) to access a remote task update server. The task update tool can communicate with the remote task update server and list available task templates, such as recommended (e.g., based on a profile) task templates and optional (e.g., task templates that do not match a profile) task templates. The user can then make a selection (e.g., by using checkboxes in a user interface) and proceed to download the selected task templates. Task templates can be selected individually or as groups of task templates. The updating itself can occur over a network (e.g., the Internet) via a public protocol such as HTTP or via a private RPC channel.

Task templates can also be discovered via a web site of available task templates. For example, a user can visit a web site and view a list of available task templates (e.g., after providing licensing information to authorize the user to view and download the task templates).

Task templates can also be discovered through notifications systems, such as an automated email or through an alert or message that appears in the management server user interface.

EXAMPLE 8 Exemplary Distribution of Task Templates

In any of the examples herein, task templates can be distributed (e.g., downloaded, transmitted, or otherwise delivered to a customer or user of the task templates) in a variety of ways. Task templates can be distributed over a network (e.g., the Internet) from a remote task update server via a web service (e.g., over a secure encrypted connection). Task templates can also be distributed on removable computer media (e.g., CD, DVD, floppy disk, flash media device).

Task templates can be distributed as individual task templates, or as groups of task templates. Task templates can be distributed based on a profile or a subscription.

EXAMPLE 9 Exemplary Display of Task Templates

In any of the examples herein, task templates can be displayed in a variety of ways. Task templates can be displayed in a user interface of a management application (e.g., as user interface elements for initiating the task templates).

Task templates can be organized for display purposes. Task templates can be grouped for display based on properties of the task templates (e.g., fields of task templates defined by a schema). For example, task templates can be grouped for display based upon the relative time (e.g., date and time) each task template was downloaded or installed (e.g., a “latest 5 tasks” list). Task templates can be display based on user-defined groupings (e.g., a “my favorite tasks” list). Task templates can also be displayed based on other criteria (e.g., how often the task template is invoked, based on an RSS (Really Simple Syndication) feed).

EXAMPLE 10 Exemplary Management of Task Templates

In any of the examples herein, task templates can be managed in a variety of ways. Cleanup rules can be created to manage task templates. For example, a cleanup rule (e.g., a business rule) can be used to remove task templates (e.g., by deleting or moving to a recycle folder) that have not been used (e.g., invoked) for a period of time (e.g., a month or year). Task templates can also be manually removed or deleted.

EXAMPLE 11 Exemplary Task Template Update System

FIG. 1 shows an exemplary system 100 for updating task templates. In the example, a task server 110 (e.g., a remote task update server) can provide task template updates (e.g., present available task template updates) to a client server 130 (e.g., a computer server of a customer). The task server 110 can obtain task template updates from a tasks database 120.

The task server 110 can be operated by a software manufacturer. The software manufacturer can periodically update task templates in the tasks database 120. A customer of the software manufacturer can connect to the task server 110 via the client server 130 to update task templates (e.g., to select and download task template updates to replace existing task templates or install new task templates).

The task server 110 can be located remotely from the client server 130. For example, the client server 130 can communicate with the task server 110 over the Internet.

EXAMPLE 12 Exemplary Task Usage System

FIG. 2 shows an exemplary system 200 for using tasks. In the example, a management application 210 (e.g., a server application) can run on a computer server 240. For example, the management application 210 can be an application for managing a collection of applications (e.g., 250, 270, and 290) (e.g., server applications) designed to operate a multi-server computer system (e.g., providing services to a business or organization). The collection of applications can include, for example, email applications, file serving applications, remote access applications, user management applications, licensing applications, and monitoring applications. Different servers of the multi-server computer system can run different applications from the collection of applications. For example, the multi-server computer system can comprise three servers: a management server (e.g., 240), an email server (e.g., 260), and a firewall server (e.g., 280). The management application 210 can be located on the management server (e.g., 240) and manage applications on the same server as well as applications on different servers (e.g., 260 and 280).

The management application 210 can be used to manage servers (e.g., by managing server applications running on the servers) using tasks 230 (e.g., where the tasks are accomplished by task templates). Tasks 230 can be stored (e.g., as task templates) in a database on a computer server (e.g., on the same server as the management application, or on a different server). Tasks 230 can also be stored in other ways (e.g., in a flat file, on removable media, as an XML schema).

The management application 210 can provide a user interface 220 allowing a user to access tasks 230 (e.g., to access task templates for accomplishing the tasks). For example, the user interface 220 of the management application 210 can display tasks 230 (e.g., displayed as user interface elements for initiating the tasks) in a variety of forms, such as a context-free task list or a contextual task list. The user interface 220 can also display entities and entity groups. For example, a user can select an entity or entity group from the user interface 220 to display contextual tasks.

From the user interface 220, a user can select (e.g., invoke) a task 230 (e.g., by selecting a user interface element for initiating the task) to manage (e.g., display information from, make a change to) an application. For example, the user can select a task 230 to manage applications 290 on the same computer server 240 that the management application 210 is operating on. The user can also select a task 230 to manage an application on a different computer server (e.g., manage applications 250 on a computer server 260, or manage applications 270 on computer server 280).

The user interface 220 can also support different options, procedures, or techniques for navigating to tasks 230 (e.g., navigating to task templates associated with, and used to accomplish, the tasks). For example, the user interface 220 can support an option for navigating to a task by displaying a context-free task (e.g., displaying a context-free task on a home page of the user interface 220 where the user has not selected an entity or entity group). The user interface 220 can support an option for navigating to a task based on a selection of an entity group and then displaying a contextual task. The user interface 220 can also support an option for navigating to a task based on a selection of an entity from an entity group and then displaying a contextual task.

EXAMPLE 13 Exemplary Method for Updating a Task Template

FIG. 3 shows an exemplary method 300 for updating a task template, and can be performed, for example, by a system such as that shown in FIG. 1. At 310, communication is initiated (e.g., from a management application running on a local client server to a remote task update server). At 320, a task template is selected (e.g., from a list of available task templates presented by the remote task update server). At 330, the selected task template is downloaded (e.g., downloaded to the local client server for use by the management application running on the local client server for managing applications of a multi-server system).

EXAMPLE 14 Exemplary Remote Task Template Update System

FIG. 4 shows an exemplary system 400 for remote task template updates. In the example, a remote task update server 410 can provide task template updates (e.g., present available task template updates) to a variable (e.g., arbitrary) number of computer networks (e.g., 440A-N). A computer network (e.g., 440A, 440B, or 440N) can be a computer network of a business or organization. A computer network (e.g., 440A, 440B, or 440N) can comprise a single network (e.g., at a single location) or multiple networks (e.g., at varying locations, such as remote office locations).

The remote task update server 410 can connect to the computer networks over a connecting network 430 (e.g., a public network such as the Internet or a private network such as a leased line).

The remote task update server can provide task template updates from a tasks database 420. Task templates can be stored in the tasks database 420 in a format defined by a schema (e.g., an XML schema).

For example, the remote update server 410 and task database 420 can be operated by a software manufacturer that sells a software package comprising applications for operating computer services of a business or organization (e.g., email services, file sharing services, firewall services, anti-virus services, licensing services). The applications of the software package can be managed by tasks which are accomplished by task templates. Customers (e.g., 440A, 440B, and 440N), such as businesses or organizations, that purchase the software package from the software manufacturer can obtain task template updates from the remote task update server 410 operated by the software manufacturer. In this way, a software manufacturer can maintain the usefulness of tasks for operating a software package sold and supported by the software manufacturer.

EXAMPLE 15 Exemplary User Interface Depicting a Task Profile Tool

FIG. 5 shows an exemplary user interface 500 depicting a task profile tool. The user interface can be displayed, for example, by a system such as that shown in FIG. 1. The task profile tool 500 can be displayed during a software setup process (e.g., displayed while installing and configuring a software package comprising multiple applications to operate a multi-server system). The task profile tool 500 can operate as a wizard.

In the user interface 530, a list of profiles 510 are displayed (e.g., to a user during the software setup process). The list of profiles 510 can include, for example, “high turnover,”“mobile users,” and “remote offices.” A user can select one or more profiles that match characteristics of the user or the user's business. For example, if the user is involved in a high employee turnover business, the user can select the “high turnover” profile and the profile will then be associated with the user, or more generally with the user's business or organization.

The profiles selected using the task profile tool 500 can be used to install and configure task templates (e.g., used to determine which task templates are to be installed during initial software setup, how they will be grouped, and how they will be displayed in a user interface). The profiles selected can also be used later to recommend task template updates.

The task profile tool 500 can be used after initial software setup has been completed. Generally, the task profile tool 500 can be used anytime a user or customer wants to change profiles associated with the user or customer.

EXAMPLE 16 Exemplary Method for Recommending Task Templates Using a Profile

FIG. 6 shows an exemplary method 600 for recommending task templates using a profile. At 610, a profile is transmitted to a task server (e.g., to a remote task update server). The profile that is transmitted to the task server can indicate a pattern of task usage (e.g., high turnover, mobile users, or remote offices). At 620, a task template is selected from a list of recommended task templates, where the recommended task templates are recommended based on the profile (e.g., where the recommended task templates have been associated with the profile by a software manufacturer). For example, if the profile is “high turnover”, the recommended task templates can comprise task templates directed to user management.

EXAMPLE 17 Exemplary Update Tasks User Interface

FIG. 7 shows an exemplary update tasks user interface 700. The user interface can be displayed, for example, by a system such as that shown in FIG. 1. In the user interface 730, a list of recommended task templates based on a profile are displayed 710. A list of recommended task templates can also be displayed based on more than one profile associated with a user or customer. The list of recommended task templates 710 can comprise individual task templates (e.g., “task template 1” and “task template 2) and task template groups (e.g., “group of task templates 1” and “group of task templates 2). The recommended task templates 710 can be associated with checkboxes in the user interface so that a user can select any of the individual or group recommended task templates.

Also displayed in the user interface 730 are user interface controls allowing a user to control the task update process. For example, the user can select a user interface control to automatically download all recommended task templates 710 displayed in the user interface 730 (e.g., using a “DOWNLOAD ALL RECOMMENDED” button). The user can select a user interface control to download only selected (e.g., via a checkbox) task templates or groups of task templates (e.g., using a “DOWNLOAD SELECTED” button). The user can select a user interface control indicating the user would like to view available task templates that have not been recommended (e.g., using a “VIEW OPTIONAL” button). Non-recommended (e.g., optional) task templates can also be displayed in the same user interface along with the recommended task templates. The user can also select a user interface control if the user is not interested in downloading any task templates (e.g., using a “CANCEL” button).

EXAMPLE 18 Exemplary Method for Updating Task Templates Using a Task Update Tool

FIG. 8 shows an exemplary method 800 for updating task templates using a task update tool (e.g., a wizard). At 810, a communication to a task update server (e.g., a remote task update server) is initiated by the task update tool (e.g., by connecting to a web service of the remote task update server over the Internet). For example, the task update tool can be a component of a management application. A task update tool can also be a stand-alone application. The task update tool can initiate communication based on input received from a user (e.g., by a user running the task update tool).

At 820, one or more task templates are selected from recommended and optional task templates displayed to a user by the task update tool. For example, the task update tool can display one or more recommended task templates (e.g., recommended based upon a profile) and one or more optional task templates (e.g., not recommended, but still available). If there are no recommended, or no optional, task templates available, then the task update tool can display only recommended task templates or only optional task templates as appropriate. A user of the task update tool can then select task templates (or groups of task templates) to download.

EXAMPLE 19 Exemplary User Interface Depicting a Task Update Tool

FIG. 9 shows an exemplary user interface 900 depicting a task update tool (e.g., a wizard). The user interface can be displayed, for example, by a system such as that shown in FIG. 1. In the user interface 930, a list of recommended task templates are displayed 910. The list of recommended task templates 910 can be displayed based on a profile of a user operating the tool. The list of recommended task templates 910 can comprise individual task templates (e.g., “task template 1” and “task template 2”) and task template groups (e.g., “group of task templates 1” and “group of task templates 2”). The recommended task templates 910 can be associated with checkboxes in the user interface so that a user can select any of the individual or group recommended task templates.

In the user interface 930, a list of optional task templates 920 can be displayed (e.g., task templates that are not recommended, but nevertheless may be of interest to a user of the task update tool). The list of optional task templates 920 can comprise individual task templates (e.g., “task template 3” and “task template 4”) and task template groups (e.g., “group of task templates 3”). The optional task templates 920 can be associated with checkboxes in the user interface so that a user can select any of the individual or group optional task templates.

Also displayed in the user interface 930 are user interface controls allowing a user to approve (e.g., via an “OK” or “UPDATE” button) or cancel (e.g., via a “CANCEL” button) the selection of task templates. If approved, the selected task templates can be downloaded.

EXAMPLE 20 Exemplary Task Template Schema

FIG. 10 shows an exemplary task template schema 1000. The task template schema can comprise various fields 1010. The task template schema can comprise a task name field (e.g., for use when displaying the task template in a user interface for selecting or invoking the task template). The task template schema can comprise a unique identifier field for uniquely identifying the task template. The task template schema can comprise a group identifier for identifying a group of the task template. The task template schema can comprise a source field for identifying a source application. The task template schema can comprise a location identifier field for identifying a user interface of an application (e.g., by way of an API of the application). The task template schema can also comprise auxiliary fields allowing for future expansion of the task template schema.

EXAMPLE 21 Exemplary Method for Updating Task Templates on a Client Server

FIG. 11 shows an exemplary method 1100 for updating task templates on a client computer (e.g., a server), and can be performed, for example, by a system such as that shown in FIG. 1. At 1110, an update request is received from a client computer. For example, the update request can be received by a remote task update server from a client computer over the Internet. The update request can comprise a profile associated with a user or customer. The update request can also include when the update actually occurs. The update can occur immediately or on a schedule.

At 1120, one or more task templates (or groups of task templates) are presented based on the request. For example, the remote task update server can present recommended task templates based on a profile received in the update request (or received prior to the update request). The remote task update server can also present optional task templates (or task templates without a recommended or optional designation, or with a different designation).

At 1130, a selection of one or more presented task templates (or groups) is received. For example, a remote task update server can receive a selection of a recommended task template by a user of the client computer.

At 1140, the selected task templates (or groups) are transmitted to the client computer. The selected task templates can be transmitted in a format defined by a schema (e.g., an XML or XrML schema).

EXAMPLE 22 Exemplary Method for Recommending Task Templates Based on a Patten of Usage

FIG. 12 shows an exemplary method 1200 for recommending task templates based on a pattern of usage. At 1210, a pattern of usage is received (e.g., by a remote task update server from a client computer over the Internet). The pattern of usage can be received as part of a profile. At 1220, a task template is recommended based on the pattern of usage. For example, if the pattern of usage indicates a high turnover business, the recommended task template can be related to adding, editing, or deleting user accounts.

EXAMPLE 23 Exemplary Method for Storing Task Templates

FIG. 13 shows an exemplary method 1300 for storing task templates. At 1310, a task template is downloaded (e.g., from a remote task update server in a format defined by a schema). At 1320, a group is assigned to the downloaded task template. For example, the group can be assigned by entering a group name in a field of the task template, where the field is group name field defined by a schema. At 1330, the downloaded task template is stored (e.g., in a tasks database in a format defined by a schema). Alternatively, the group can be assigned to the downloaded task template after it has been stored.

EXAMPLE 24 Exemplary Entity

In any of the examples herein, an entity can be an object (e.g., an object associated with a computer network), a solution (e.g., a group of entities), or one or more tasks. For example, an entity can be a computer (e.g., a desktop, laptop, server), a user, a printer, a network device (e.g., switch, hub, router), a configuration setting, a license, or any other type of entity. Entities can be grouped together in entity groups.

Tasks can be performed on an entity. For example, an entity can be selected (e.g., by a user in a user interface). Selecting an entity (e.g., clicking or right-clicking on an icon representing the entity in a user interface) can display a list of tasks (e.g., a list of user interface elements for initiating the tasks). The list of tasks can be associated with the entity. A task from the list of tasks can be selected and, using an associated task template, a user interface can be displayed for completing the task.

EXAMPLE 25 Exemplary Entity Group

In any of the examples herein, an entity group can comprise a collection of entities. The collection of entities can be homogeneous or heterogeneous. For example, a homogeneous users entity group can comprise a collection of user entities. A heterogeneous email entity group can comprise a collection of entities that participate in email activities, such as: users, email servers, client email applications, and server email applications.

The collection of entities can be related. For example, a network entity group can comprise a collection of entities related to the network (e.g., servers, user computers, printers).

Tasks can be performed on an entity group. For example, an entity group can be selected (e.g., by a user in a user interface). Selecting an entity group (e.g., clicking on an icon representing the entity group) can display a list of tasks (e.g., a list of user interface elements for initiating the tasks). The list of tasks can be associated with the entity group. A task from the list of tasks can be selected and, using an associated task template, a user interface can be displayed for completing the task. For example, selecting a network entity group can display a task for viewing bandwidth usage across the network (e.g., across the entities comprising the network entity group).

EXAMPLE 26 Exemplary Contextual Task

In any of the examples herein, a task can be a contextual task. A contextual task can be a task that is associated with a selected entity or entity group (e.g., the task applies to or will be performed on the selected entity or entity group). For example, if a user is presented with a user interface displaying a number of entity groups, the user can select one of the entity groups. Once the user has selected one of the entity groups, a list of contextual tasks can be displayed (e.g., a list of user interface elements for initiating the contextual tasks). The list of tasks is contextual because it is associated (e.g., scoped) with the selected entity group. For example, if the user selects a network entity group, the list of contextual tasks would be associated to the network entity group. An example of contextual tasks associated with a network entity group can be: view performance, view alerts, and view events.

Similarly, for example, if a user is presented with a user interface displaying a number of entities, the user can select one of the entities. Once the user has selected one of the entities, a list of contextual tasks can be displayed. The list of tasks is contextual because it is associated (e.g., scoped) with the selected entity (e.g., the tasks apply to or will be performed on the selected entity). For example, if the user selects a specific computer server from a computer servers entity group, the list of contextual tasks would be associated with the specific computer server. An example of contextual tasks associated with a specific computer server entity can be: approve updates, configure web server, deploy new software package, view performance, view alerts, and view events. For example, the approve updates contextual task can allow a user to approve updates for the selected computer server entity.

EXAMPLE 27 Exemplary Context-Free Task

In any of the examples herein, a task can be a context-free task. A context-free task can be a task that is displayed (e.g., as a user interface element for initiating the context-free task) regardless of whether an entity or entity group is selected (e.g., a context-free task is not tied to the display of an entity or an entity group). Therefore, context-free tasks can be displayed independently of contextual tasks. A context-free task can also be known as a global task.

For example, a user can be presented with a user interface in which there are no entities or entity groups selected. A list of context-free tasks can be displayed in the user interface. For example, the list of context-free tasks can include: approve updates on server 1, review email license usage, and view file server performance.

Context-free tasks can also be displayed at the same time (e.g., simultaneously, concurrently, contemporaneously) as contextual tasks. For example, a list of context-free tasks can be displayed in a user interface (where there are no entities or entity groups selected). A user can then select an entity or entity group which causes display (e.g., in a separate area of the user interface) of a list of contextual tasks. The list of context-free tasks can have a label identifying the list, as can the list of contextual tasks. The context-free tasks and contextual tasks can also be mixed (e.g., in a single list of tasks).

Displaying a list of contextual tasks can cause a list of context-free tasks to be removed (e.g., from being displayed in a user interface). For example, if a user selects an entity or entity group, then a currently displayed list of context-free tasks can be removed and a list of contextual tasks displayed instead (e.g., replaced by the list of contextual tasks in the same area of the user interface, or in a different area of the user interface).

EXAMPLE 28 Exemplary Pivot

In any of the examples herein, a pivot can be the ability to switch between different options, procedures, or techniques of accessing, displaying, navigating to, or viewing entity groups, entities, or tasks (e.g., a task template, or instance of a task template, associated with the task). For example, a user can be presented with two options for accessing a task template, and the user can pivot (e.g., switch, alternate, change) between the two options. One of the two options can represent task navigation via a context-free task list, and the other option can represent task navigation via a contextual task list.

EXAMPLE 29 Exemplary User Interface Depicting Display of Task Templates

FIG. 14 shows an exemplary user interface 1400 depicting display of task templates. The user interface can be displayed, for example, by a system such as that shown in FIG. 3. In the user interface 1400, a number of entity groups are displayed: a network entity group 1410, a users entity group 1420, and a licensing entity group 1430. In the user interface 1400, the network entity group 1410 has been selected. Based on the selected network entity group 1410, a number of entities 1440 associated with the selected network entity group are displayed.

In the user interface 1400, a number of “new tasks” are displayed in a list 1450. For example, the “new tasks” 1450 can be task templates that have been recently updated. The tasks of the “new tasks” list can be contextual tasks, context-free tasks, or a mixture of both. The management application can use a visual cue, such as an icon, to distinguish a new task from one of the tasks that ships with the management server.

In the user interface 1400, a number of “network tasks” are displayed 1460. The “network tasks” can be contextual tasks displayed based on the selection of the network entity group 1410.

Also displayed in the user interface 1400 are a number of tasks (e.g., a user of a management application that operates the user interface) can select a number of task templates for display in the user interface 1400 under a user-defined title, such as “my tasks” 1470. These tasks can represent tasks that the user performs frequently. The tasks of the “my tasks” list 1470 can be contextual tasks, context-free tasks, or a mixture of both.

EXAMPLE 30 Exemplary Method for Completing a Task

FIG. 15 shows an exemplary method 1500 for completing a task. At 1510, a task template is displayed (e.g., as an instance of the task template). For example, the task template can be displayed as a result of a user selecting a context-free task from a user interface. The task template can also be displayed as a result of a user selecting a contextual task from a user interface (e.g., after having selected an entity group or entity).

At 1520, user input is received. For example, the user input can comprise information entered by the user into a form (e.g., information such as user name, real name, and password entered in an add new user form).

At 1530, the task is completed. For example, the user can complete an add new user task by entering information into a form and clicking on an “ADD” or “OK” button.

EXAMPLE 31 Exemplary Server Applications

In any of the examples herein, server applications can be any software installed on a server. For example, server applications can include any server application offering a service for use by a client. In practice, such server applications can include file sharing services, email servers, licensing services, directory services, firewall services, anti-spam services, anti-virus detection services, networking services (e.g., services for managing identities and relationships that make up a network), and the like.

Server applications can also include operating system programs, such as an operating system, operating system enhancements, or both.

EXAMPLE 32 Exemplary Multi-Server System for Performing Tasks

FIG. 16 shows an exemplary multi-server system 1600 for performing tasks. In the example, a management application 1610 (e.g., a server application) can run on a computer server 1670A. For example, the management application can comprise a data manager 1615 for managing a number of computer servers by managing server applications on the computer servers (e.g., server application 1640A on server 1670A, server application 1640B on server 1670B, and server application 1640N on server 1670N).

The server applications (1640A- 1640N) can include, for example, server applications for providing computer services to a business or organization, such as: email applications, file serving applications, remote access applications, user management applications, licensing applications, anti-virus applications, and monitoring applications. Different servers of the multi-server system can perform specific services for a business or organization by running different server applications. For example, the multi-server system can comprise three servers: a management server (e.g., 1670A) running a file service application (e.g., 1640A), an email server (e.g., 1670B) running an email application (e.g., 1640B), and a firewall server (e.g., 1670N) running an anti-virus application (e.g., 1640N).

The data manager 1615 can manage a server application (e.g., 1640A, 1640B, or 1640N) on a server (e.g., 1670A, 1670B, or 1670N) by communicating with an API of the server application. For example, a user management server application can provide an API for displaying various user interfaces within the user management application (e.g., a user interface for adding users, a user interface for deleting users, and a user interface for resetting a user's password).

The management application 1610 can provide a user interface 1620 allowing a user to manage the servers and applications of the multi-server system 1600 using tasks 1616. For example, the user interface 1620 of the management application 1610 can display tasks 1616 (e.g., displayed as user interface elements for initiating the tasks) in a variety of forms, such as a context-free task list or a contextual task list. The user interface 1620 can also display entities and entity groups (e.g., from an entities database 1618). For example, a user can select an entity or entity group from the user interface 1620 to display contextual tasks.

The tasks 1616 can be stored (e.g., as task templates) in a database. The task templates can be used to accomplish (e.g., complete) a task by directing a user to a user interface for accomplishing the task. For example, a task template can comprise a location variable, where the location variable represents a user interface of a server application by way of an API of the server application.

For example, the management application 1610 can display, in the user interface 1620, an entity from the entities database 1618, receive a selection of the entity from a user, display a task from the tasks database 1616, and receive a selection of the task from the user. The management application 1610 can then, via the data manager 1615, using a location variable from a task template associated with the selected task, connect to an API of a server application (e.g., 1640A, 1640B, or 1640N) and display a user interface which the user can then use to complete the selected task.

Server applications (e.g., 1640A-N) can also provide services (e.g., email services, file sharing services, user services) to user computers (e.g., 1690A-N).

EXAMPLE 33 Exemplary Computing Environment

FIG. 17 illustrates an example computing environment 1700 that can be used to implement any of the technologies described herein. The computing environment includes a network 1710. The network 1710 can comprise servers 1720 (e.g., computer servers), services 1730 (e.g., computer services), users 1740 (e.g., general computer users, IT administrators, employees), and devices 1750 (e.g., desktop or laptop computers, printers, copiers, scanners).

The network 1710 can connect to other networks, such as 1770 and 1780, through connecting network 1760. For example, the connecting network 1760 can comprise a wide area network such as the Internet or a local network. The connecting network can comprise various network hardware, protocols, and topologies.

EXAMPLE 34 Exemplary General Purpose Computer System

FIG. 18 illustrates an example of a computer system 1800 that can be used to implement any of the technologies described herein. The computer system includes a personal computer 1820, including a processing unit 1821, a system memory 1822, and a system bus 1823 that interconnects various system components including the system memory to the processing unit 1821. The system bus may comprise any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using a bus architecture such as PCI, VESA, Microchannel (MCA), ISA and EISA, to name a few. The system memory includes read only memory (ROM) 1824 and random access memory (RAM) 1825. A basic input/output system 1826 (BIOS), containing the basic routines that help to transfer information between elements within the personal computer 1820, such as during start-up, is stored in ROM 1824. The personal computer 1820 further includes a hard disk drive 1827, a magnetic disk drive 1828, e.g., to read from or write to a removable disk 1829, and an optical disk drive 1830, e.g., for reading a CD-ROM disk 1831 or to read from or write to other optical media. The hard disk drive 1827, magnetic disk drive 1828, and optical disk drive 1830 are connected to the system bus 1823 by a hard disk drive interface 1832, a magnetic disk drive interface 1833, and an optical drive interface 1834, respectively. The drives and their associated computer-readable media provide nonvolatile storage of data, data structures, computer-executable instructions (program code such as dynamic link libraries and executable files), etc. for the personal computer 1820. Although the description of computer-readable media above refers to a hard disk, a removable magnetic disk and a CD, it can also include other types of media that are readable by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, and the like.

A number of program modules may be stored in the drives and RAM 1825, including an operating system 1835, one or more application programs 1836, other program modules 1837, and program data 1838. A user may enter commands and information into the personal computer 1820 through a keyboard 1840 and pointing device, such as a mouse 1842. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 1821 through a serial port interface 1846 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). A monitor 1847 or other type of display device is also connected to the system bus 1823 via an interface, such as a display controller or video adapter 1848. In addition to the monitor, personal computers typically include other peripheral output devices (not shown), such as speakers and printers.

The personal computer 1820 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 1849. The remote computer 1849 may be a server, a router, a peer device or other common network node, and typically includes many or all of the elements described relative to the personal computer 1820, although only a memory storage device 1850 has been illustrated in FIG. 18. The logical connections depicted in FIG. 18 include a local area network (LAN) 1851 and a wide area network (WAN) 1852. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

When used in a LAN networking environment, the personal computer 1820 is connected to the local network 1851 through a network interface or adapter 1853. When used in a WAN networking environment, the personal computer 1820 typically includes a modem 1854 or other means for establishing communications over the wide area network 1852, such as the Internet. The modem 1854, which may be internal or external, is connected to the system bus 1823 via the serial port interface 1846. In a networked environment, program modules depicted relative to the personal computer 1820, or portions thereof, may be stored in the remote memory storage device. The network connections shown are merely examples and other means of establishing a communications link between the computers may be used.

EXAMPLE 35 Exemplary Automated Methods

Any of the methods described herein can be performed via one or more computer-readable media having computer-executable instructions for performing such methods. Operation can be fully automatic, semi-automatic, or involve manual intervention.

EXAMPLE 36 Exemplary Combinations

The technologies of any example described herein can be combined with the technologies of any one or more other examples described herein.

EXAMPLE 37 Exemplary Alternatives

In view of the many possible embodiments to which the principles of the disclosed invention may be applied, it should be recognized that the illustrated embodiments are only preferred examples of the invention and should not be taken as limiting the scope of the invention. Rather, the scope of the invention is defined by the following claims. We therefore claim as our invention all that comes within the scope and spirit of these claims. 

1. A computer implemented method for updating task templates on a client server from a remote task update server, wherein the task templates are used to accomplish tasks for managing applications of a multi-server system, the method comprising: using the client server: tracking, by the client server, a pattern of task usage by a user of the client server, wherein the tracking the pattern of task usage comprises monitoring which tasks, and associated task templates, are used by the user of the client server to manage software applications of the multi-server system; initiating a communication with the remote task update server from the client server, wherein initiating the communication with the remote task update server comprises transmitting a profile from the client server to the remote task update server, wherein the profile indicates the pattern of task usage by the user of the client server; based on a list of available task templates presented by the remote task update server, selecting a task template from the list of available task templates, wherein the list of available task templates are recommended, by the remote task update server, based on the profile; and downloading the selected task template from the remote task update server to the client server, wherein the selected task template is downloaded in a format defined by a schema, wherein the schema comprises the following fields: a name field indicating a task name of the task template; a unique identifier field for unique identifying the task template; a group identifier field for identifying a group of the task template; and a location identifier field for identifying a user interface in an application.
 2. The method of claim 1 wherein initiating the communication with the remote task update server comprises initiating the communication at a time based on a subscription parameter, wherein the subscription parameter comprises a frequency for initiating communication with the remote task update server.
 3. The method of claim 1 wherein initiating the communication with the remote task update server comprises initiating the communication via a task update tool, wherein the list of available task templates comprises a task template identified as recommended by the remote task update server and a task template identified as optional by the remote task update server, and wherein the list of available task templates is displayed to a user of the client server by the task update tool.
 4. The method of claim 1 wherein initiating the communication with the remote task update server comprises transmitting licensing information to the remote task update server.
 5. The method of claim 1 further comprising: after downloading the selected task template, displaying, in a management application on the client server, a favorite tasks list comprising a user interface element for invoking the selected task template.
 6. The method of claim 1 further comprising: after downloading the selected task template, receiving, from a user of the client server, a group name; and associating the selected task template with the group name.
 7. The method of claim 1 further comprising: after downloading the selected task template, storing the downloaded selected task template in a database, wherein the downloaded selected task template is stored in the format defined by the schema.
 8. The method of claim 1 wherein initiating the communication with the remote task update server comprises initiating the communication, via an encrypted protocol, with a web service provided by the remote task update server.
 9. The method of claim 1 further comprising: responsive to selecting the task template from the list of available task templates, downloading a computer executable file associated with the selected task template.
 10. The method of claim 1 further comprising: assigning a group name to the downloaded task template; and after assigning the group name, storing the downloaded task template in a database, wherein the downloaded task template is stored in the format defined by the schema.
 11. The method of claim 10 further comprising: after storing the downloaded task template, deleting the downloaded task template from the database, wherein the deleting is based on a task template cleanup rule.
 12. The method of claim 10 further comprising: after storing the downloaded task template, displaying a user interface element for invoking the downloaded task template in a location of a user interface defined by a user of the user interface.
 13. The method of claim 10 further comprising: after storing the downloaded task template, displaying a user interface element for invoking the downloaded task template in a user interface; receiving a selection of the user interface element for invoking the downloaded task template by a user of the user interface; and responsive to the selection of the user interface element for invoking the downloaded task template, displaying an application user interface identified by the location identifier field of the downloaded task template.
 14. A computer implemented method for updating task templates on a client server from a remote task update server, the method comprising: by the remote task update server: receiving an update request from the client server, wherein receiving the update request from the client server comprises receiving a profile from the client server, wherein the profile indicates a pattern of task usage by a user of the client server, wherein the pattern of task usage is generated on the client server by monitoring which tasks, and associated task templates, are used by the user of the client server to manage software applications of a multi-server system; based on the update request, presenting a task template, wherein the presented task template is recommended based on the profile; receiving a selection of the presented task template; and transmitting the selected task template to the client server, wherein the selected task template is in a format defined by a schema, wherein the schema comprises the following fields: a name field indicating a task name of the task template; a unique identifier field for unique identifying the task template; a group identifier field for identifying a group of the task template; and a location identifier field for identifying a user interface in an application.
 15. The method of claim 14 further comprising: based on the update request, presenting a group of task templates, wherein the group of task templates comprises a plurality of task templates; receiving a selection of the group of task templates; and transmitting the selected group of task templates to the client computer, wherein the plurality of task templates comprising the selected group of task templates are in the format defined by the schema.
 16. The method of claim 14 wherein the presented task template is based on a last time an update request was received from the client computer.
 17. A computer-readable medium storing computer-executable instructions for performing a computer implemented method for updating task templates on a client server from a remote task update server, wherein the task templates are used to accomplish tasks for managing applications of a multi-server system, the method comprising: Tracking, by the client server, a pattern of task usage by a user of the client server, wherein the tracking the pattern of task usage comprises monitoring which tasks, and associated task templates, are used by the user of the client server to manage software applications of the multi-server system; initiating a communication with the remote task update server from the client server, wherein initiating the communication with the remote task update server comprises transmitting a profile from the client server to the remote task update server, wherein the profile indicates the pattern of task usage by the user of the client server; based on a list of available task templates presented by the remote task update server, selecting a task template from the list of available task templates, wherein the list of available task templates are recommended, by the remote task update server, based on the profile; and downloading the selected task template from the remote task update server to the client server, wherein the selected task template is downloaded in a format defined by a schema, wherein the schema comprises the following fields: a name field indicating a task name of the task template; a unique identifier field for unique identifying the task template; a group identifier field for identifying a group of the task template; and a location identifier field for identifying a user interface in an application. 